Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines which are not met ❌

• Name does not meet all of the following: starts with an upper-case letter, ASCII alphanumerics only, not all letters are upper-case.

• Name is not at least 5 characters long

• Package name similar to 24 existing packages.

  Similar package names

  1. Similar to GAP. Damerau-Levenshtein distance 1 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1. Normalized visual distance 0.70 is at or below cutoff of 2.50.
  2. Similar to Clp. Damerau-Levenshtein distance 2 is at or below cutoff of 2. Damerau-Levenshtein distance 1 between lowercased names is at or below cutoff of 1.
  3. Similar to GCP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  4. Similar to DSP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  5. Similar to CRC. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  6. Similar to C3D. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  7. Similar to BAT. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  8. Similar to COPT. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  9. Similar to Cxx. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  10. Similar to PAPI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  11. Similar to Cbc. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  12. Similar to XAM. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  13. Similar to CSV. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  14. Similar to RAI. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  15. Similar to CAOS. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  16. Similar to MAT. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  17. Similar to WAV. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  18. Similar to CGAL. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  19. Similar to FCA. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  20. Similar to CSDP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  21. Similar to DAQP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  22. Similar to XPA. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  23. Similar to UMAP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.
  24. Similar to SCIP. Damerau-Levenshtein distance 2 is at or below cutoff of 2.

3. Needs action: here's what to do next

1. Please try to update your package to conform to these guidelines. The General registry's README has an FAQ that can help figure out how to do so.
2. After you have fixed the AutoMerge issues, simply retrigger Registrator, the same way you did in the initial registration. This will automatically update this pull request. You do not need to change the version number in your Project.toml file (unless the AutoMerge issue is that you skipped a version number).

If you need help fixing the AutoMerge issues, or want your pull request to be manually merged instead, please post a comment explaining what you need help with or why you would like this pull request to be manually merged. Then, send a message to the #pkg-registration channel in the public Julia Slack for better visibility.

4. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

The CAP project was initiated in 2015 as part of two dissertations in computer algebra. CAP is the name of the core package. It is already part of the GAP distribution under this three-letter name. CAP.jl is now completely independent from GAP (and also from the registered GAP.jl). The package CAP.jl gives native Julia access to the core package of the CAP project, which, unlike GAP.jl, can finally run under Windows without the need of the linux subsystem. This will allow for a wider user base in computer algebra.

[noblock] Not a fan of these three-letter acronyms as package names, but I suppose, having GAP, the "spin-off" CAP follows a pattern. So I guess this should be okay.

P.S.: But you'll need support from someone with full merge permissions, which isn't me

[noblock] Not a fan of these three-letter acronyms as package names, but I suppose, having GAP, the "spin-off" CAP follows a pattern. So I guess this should be okay.

Thank you very much, Michael.

P.S.: But you'll need support from someone with full merge permissions, which isn't me

Do I need to contact a specific person?

After the three-day waiting periods ends, you can ask in the #pkg-registration channel on Slack